Thanks for your reply. Somehow - I don't know exactly how - I got my "1920 1080 32" (native) resolution to work in Vavoom 1.30. After about the third or fourth try, my Vlaunch "SetResolution" worked and continued to do so throughout the entire Strife game (until I got to the end and discovered the Macil-Spectre-Sigil bug.) As I couldn't get the "SetResolution" command to work with Vavoom 1.32, I downgraded to Vavoom 1.30 so that I could play "Doom: The Plutonia Experiment " (until I can get up the patience to play Strife through from beginning to end, again) in my monitors native resolution only to discover that the "SetResolution" that gave me "1920 1080 32" in Strife didn't work anymore (at least with the Plutonia WAD.)

I just downloaded and installed Vavoom version 1.32 in order to solve my Strife Sigil spectre crash problem, and I'm getting the following error when I attempt to run Strife from Vlaunch: Default texture -noflat- not found Stack trace: VTextureManager::Init <- R_InitTexture <- HostInit I uncompressed the new version into a clean directory and, since there was no "basev" directory created, I copied the "basev" directory over from the 1.30 Vavoom version. Has anybody else had this problem?

There should be a 'basev' directory, the error you are getting could be because you are using 'basev' from the old version on the new one.

You're absolutely right. I came back to post about finding the answer to my problem and saw your post, which basically sums it up. For some reason, my Winzip "Use folder names" extraction flag became unchecked between the Vavoom 1.30 and 1.32 installations so that the 1.32 basev directory wasn't created (and, as you point out, the basev directories from the two versions are not compatible, apparently.) Anyway, once the new Vavoom 1.32 basev directory was created, I was able to Vlaunch Strife. My only problem now is that I can't get this version to SetResolution to 1920 1080 32. The highest it seems to go is 1650 1080 32 (which I found out after I gave up trying to do this from Vlaunch and tried setting the resolution in the console.) I had no problems with this in Vavoom version 1.30.

There will be some changes in the way the renderers set resolutions, but it will require a bit more time for development, right now things are progressing a bit slow.